I ran into an issue wherein the SentryExceptions and SentryThreads properties on SentryEvent can return open JsonElement objects instead of their actual properties. If the JsonDocument holding those elements is not disposed, we get a memory leak. But also, if the document is disposed, we can't deserialize the data without getting an ObjectDisposedException. The root cause turned out to be an un-materialized IEnumerable on those properties coming from SentryEvent.FromJson.

The tests were hiding this, because we were using our Json.Parse(string) helper function, which was using .Clone(), so the elements wouldn't have been disposed with the document. Since cloning is semi-costly, I revised the helper methods to avoid it, by passing in a factory method delegate instead and using it to return a concrete object instead of a JsonElement.

Only one test failed with the change to the JSON helpers, which was for the issue had already found on SentryEvent. Adding .ToList() in the correct place made the test pass again.

So - part fix, part perf improvement.